|
1. Defining the test environment
Each test level requires a test environment in order to execute the tests. This environment is generally composed of the
following components:
-
Hardware
-
Software
-
Interfaces
-
Environment data
-
System management tools
-
Processes.
The environment should be composed and set up in such a way as to facilitate, on the basis of the test results
obtained, the best estimate of the degree to which the test object meets the set requirements. The environment has a
considerable influence on the quality, duration and costs of the test process. In order to manage the test environment
effectively, it is often separate from the development or production environment. Moreover, each test level sets its
environment different requirements.
At www.tmap.net, a checklist “Test environments” is available that
can be of assistance in defining the test environment. If the test environment already exists, for example in a
maintenance process, it may be sufficient to refer to this and to mention any adjustments to be made.
|
2. Defining the test tools
| It is established which test tools are required. Test tools can provide support with most test activities. Besides the
familiar test tools, such as test management, record & playback and defect management tools, you should also think of
small, freeware or even self-built tools. Such tools can often be implemented for a small investment in time, but can be
extremely valuable. The Internet is invaluable for seeking out freeware tools (search, for example, for “freeware test
tool”). For self-built tools, it is advisable to consult the developers; they often already have such tools, otherwise they
may be able to make them with very little effort. |
3. Defining the office setup
The office infrastructure required for testing (workrooms, meeting rooms, telephones, PCs, network connections, office
software, printers, etc.) is defined in outline. This concerns an office setup in the widest sense, since testers, too,
need to carry out their work in the right circumstances. A checklist for the office setup can be found at www.tmap.net.
The appropriate and timely setting up of the office infrastructure will mean that all kinds of efficiency losses, such
as relocations, waiting times and unproductive hours can be kept to a minimum. A bad example in this connection is if
the testers have to be physically too far removed from each other and the rest of the project. An adequate setup of the
workplaces also has a positive infl uence on the quality of the test process. This concerns, for example, the quality
of both the internal and external communication and the motivation and productivity of the people involved.
|
4. Establishing infrastructure planning
| The test manager documents the agreements made and creates a general plan containing the timings of the availability of the
various facilities. The further ordering and arranging of the infrastructure comes under the responsibility of the test
infrastructure coordinator. |
|
